Universal Access To All Knowledge
Home Donate | Store | Blog | FAQ | Jobs | Volunteer Positions | Contact | Bios | Forums | Projects | Terms, Privacy, & Copyright
Search: Advanced Search
Anonymous User (login or join us)
Upload

Reply to this post | See parent post | Go Back
View Post [edit]

Poster: Administrator, Curator, or StaffDiana Hamilton Date: May 11, 2006 5:05am
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

"dont fix something that isn't broken"

You're saying you don't remember all the "sorry it's broken" times up to now?! Glad to see some of the old problems go.

Reply to this post
Reply [edit]

Poster: Hatta Date: May 11, 2006 5:32am
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

I realize you're all trying to make this a better place through this transition, but it just seems like curing the disease by killing the patient.

If you want to keep the users from freaking out, give us some warning and let us do some testing before changing over. Dropping browse by year is a big, BIG usability change which would have been noticed if you did just a little beta testing. Then you could have fixed it BEFORE moving the new system to production. And then everyone would not freak out, and you'd be having a much better day. :)

I'm still trying to figure out how to browse by year for bands with mp3s. Any ideas?

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or Staffgreenone Date: May 11, 2006 5:42am
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

If you want to keep the users from freaking out, give us some warning and let us do some testing before changing over.

This may sound cold, but... this site really isn't about the users (of which I am one - just a user, not an admin); it's about the content, and preserving that content. And the content was REALLY suffering under the old system. Entire shows disappearing, bug reports left right and center, and not enough curators to keep up with it all. To continue with your metaphor, the patient was sick, but the delays in moving it over to the new system was making it much sicker by the day, as the old system was creaky and required much more intervention by the few curators with access.

Reply to this post
Reply [edit]

Poster: Dancing Salmon Date: May 11, 2006 10:50pm
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

I can understand that the engine behind the interface had to be changed (though I never noticed problems myself).

But that doesn't mean that the user interface, the front-end, had to change in all the ways it has. Indeed, the old navigation tools are still available, only hidden -- so obviously they still work.

I think the "mistake" here was changing both the internal stuff -- database, admnistrative/curatorial tools -- and the user interface at the same time. It would have caused less freakout to hold off on the latter until the former changes settled down, and then to seek user input or make a beta version available for user comment alongside the old interface.

I can see that it may have been less work to do both at the same time, and that the programmers were actively trying to give us a nifty new interface that would let us do all sorts of neat new programmerly things (hierarchical is so last decade :-)... but those aren't necessarily what the user wants to do.

Reply to this post
Reply [edit]

Poster: Administrator, Curator, or StaffDiana Hamilton Date: May 11, 2006 11:31pm
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

I'm not a computer person, but AFAIK the user interface is tied to the backend stuff. That was true of the old system too.

Reply to this post
Reply [edit]

Poster: direwolf0701 Date: May 11, 2006 5:45am
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

i am just curious as to how the "new system" is going to fix these "bugs" and make navigation easier for the user (like me). not complaining, just trying to figure out the new changes. i am not good with change :-P

Reply to this post
Reply [edit]

Poster: J.C. Date: May 11, 2006 11:31am
Forum: etree Subject: Re: Why change something that was so good and make it so bad?

"this site really isn't about the users"

By that logic, why spend the bandwidth to make it public at all?

Sorry, but a *public* library is about the users.

Terms of Use (10 Mar 2001)